Skip to content

Update ols-creating-the-credentials-secret-using-web-console.adoc #91378

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
nikhilprajapati-world wants to merge 1 commit into from
Closed

Update ols-creating-the-credentials-secret-using-web-console.adoc #91378

nikhilprajapati-world wants to merge 1 commit into from

Conversation

@nikhilprajapati-world
Copy link
Contributor

@nikhilprajapati-world nikhilprajapati-world commented Apr 1, 2025 •
edited
Loading

There should be a one liner in the Red Hat Lightspeed documentations about the api_token when used with data in secrets.

Something like this: "The apitoken is base64 encoded"

https://docs.redhat.com/en/documentation/red_hat_openshift_lightspeed/1.0tp1/html/configure/ols-configuring-openshift-lightspeed#ols-configuring-openshift-lightspeed

Version(s):

Issue:
https://issues.redhat.com/browse/OSDOCS-13916

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

@nikhilprajapati-world
Update ols-creating-the-credentials-secret-using-web-console.adoc
b8c49b6 
There should be a one liner in the Red Hat Lightspeed documentations about the api_token when used with data in secrets. 

Something like this: "The apitoken is base64 encoded"
@openshift-ci openshift-ci bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Apr 1, 2025
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Apr 1, 2025 •
edited
Loading

🤖 Tue Apr 01 07:33:44 - Prow CI generated the docs preview:

https://91378--ocpdocs-pr.netlify.app/openshift-lightspeed/latest/configure/ols-configuring-openshift-lightspeed.html

@nikhilprajapati-world
Copy link
Contributor Author

nikhilprajapati-world commented Apr 1, 2025

/retest

@openshift-ci
Copy link

openshift-ci bot commented Apr 1, 2025

@nikhilprajapati-world: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/validate-asciidoc b8c49b6 link true /test validate-asciidoc

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 14, 2025
@openshift-merge-robot
Copy link

openshift-merge-robot commented Apr 14, 2025

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-bot
Copy link

openshift-bot commented Jul 13, 2025

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 13, 2025
@openshift-bot
Copy link

openshift-bot commented Aug 13, 2025

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 13, 2025
@openshift-bot
Copy link

openshift-bot commented Sep 12, 2025

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci bot closed this Sep 12, 2025
@openshift-ci
Copy link

openshift-ci bot commented Sep 12, 2025

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@nikhilprajapati-world @ocpdocs-previewbot @openshift-merge-robot @openshift-bot